Update condition for when broker transport has no throughput connection settings#2265
Merged
Update condition for when broker transport has no throughput connection settings#2265
Conversation
abparticular
approved these changes
Mar 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the conditions on the throughput connection setup page to match the conditions that control the two lower sections.
This change avoids displaying the intro paragraph when neither of the two lower sections will be displayed, which happens when a broker transport has no settings to configure.
The RabbitMQ transport will no longer have separately configurable settings once Particular/ServiceControl#4755 ships as part of a ServiceControl release.